Version Packages - #24
Conversation
6419bd7 to
bc255c5
Compare
bc255c5 to
685252f
Compare
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 685252f. Configure here.
| { | ||
| "name": "subtext", | ||
| "version": "0.10.2", | ||
| "version": "0.10.3", |
There was a problem hiding this comment.
Lockfile version left unsynced
Low Severity
package.json was bumped to 0.10.3, but package-lock.json still records 0.10.2 at the top-level version and packages[""].version. The two files are out of sync, so a later npm install rewrites the lockfile and committed version metadata no longer matches the release.
Reviewed by Cursor Bugbot for commit 685252f. Configure here.
changeset version bumps package.json but not package-lock.json, so the Version Packages PR left the lockfile's top-level and root-package (packages[""]) version at the old value — a later npm install would rewrite it and the release's version metadata would no longer match (Bugbot flagged this on the v0.10.3 PR #24). Extend sync-manifest-versions.mjs to also write the version into package-lock.json's two version fields: hermetic (no npm install / no network), idempotent, and consistent with how the per-harness manifests are already synced. Signed-off-by: Joel Webber <joel@fullstory.com>
1 participant
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
subtext@0.10.3
Patch Changes
.cursor-plugin/marketplace.json) listing only the root Subtext plugin. Cursor-style marketplace indexers read.cursor-plugin/marketplace.jsonbefore.claude-plugin/marketplace.json; without it they fall through to the Claude listing, where the externalsubtext-verifyGitHub source reference either fails parsing or causes Subtext Verify to be surfaced instead of Subtext. Also teachsync-manifest-versions.mjsto keep the new manifest's version in sync.Note
Low Risk
Version and marketplace manifest metadata only; no application logic or security-sensitive code paths change in this PR.
Overview
Automated Changesets release that bumps subtext from
0.10.2to0.10.3and aligns that version acrosspackage.json, Claude/Codex/Cursor plugin manifests, andgemini-extension.json.CHANGELOG.mdrecords the patch for this release: adding.cursor-plugin/marketplace.jsonso Cursor-style indexers list only the root Subtext plugin (avoiding fall-through to the Claude marketplace entry withsubtext-verify), plus keeping that manifest’s version in sync viasync-manifest-versions.mjs(from the merged changeset). The consumed changeset file.changeset/cursor-marketplace-manifest.mdis removed as part of versioning.No runtime or MCP tool behavior changes in this diff—metadata, changelog, and release bookkeeping only.
Reviewed by Cursor Bugbot for commit 685252f. Bugbot is set up for automated code reviews on this repo. Configure here.